UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

BMC MAINVIEW for z/OS STC data sets are not properly protected.


Overview

Finding ID Version Rule ID IA Controls Severity
V-224424 ZMVZR001 SV-224424r868506_rule Medium
Description
BMC MAINVIEW for z/OS STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
STIG Date
z/OS BMC MAINVIEW for z/OS for RACF Security Technical Implementation Guide 2022-10-07

Details

Check Text ( C-26101r868504_chk )
Refer to the following report produced by the Data Set and Resource Data Collection:

- SENSITVE.RPT(MVZSTC)

Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:

- PDI(ZMVZ0001)

Verify that the accesses to the BMC MAINVIEW for z/OS STC data sets are properly restricted.

___ The RACF data set rules for the data sets restricts READ access to auditors and authorized users.

___ The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to systems programming personnel.

___ The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to the BMC MAINVIEW for z/OS's STC(s) and/or batch user(s).
Fix Text (F-26089r868505_fix)
The ISSO will ensure that update and allocate access to BMC MAINVIEW for z/OS STC data sets is limited to systems programmers and/or BMC MAINVIEW for z/OS's STC(s) and/or batch user(s) only. Read access can be given to auditors and authorized users.

The installing systems programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update and/or alter access for specific data sets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.

Data sets to be protected will be:
SYS3.BMCVIEW (data sets that are altered by the product's STCs, this can be more specific)

The following commands are provided as a sample for implementing data set controls:

ad 'SYS3.BMCVIEW.**' uacc(none) owner(sys3) -
audit(failures(read)) -
data('Vendor DS Profile: BMC MAINVIEW for z/OS')
pe 'SYS3.BMCVIEW.**' id( MAINVIEW STCs) acc(a)
pe 'SYS3.BMCVIEW.**' id( authorized users) acc(r)

setr generic(dataset) refresh